Systems and methods for cloud based pin pad device gateway

ABSTRACT

A method of processing payment transactions includes receiving a connection request from a client device, determining whether a gateway is available for the client device, creating a connection between the client device and a gateway, the gateway being a previously existing gateway or a newly generated gateway, creating a message filter for the client device on a message bus, listening for messages on the message bus and transmitting the message to the client device by way of the gateway upon finding a message on the message bus matching the message filter.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This patent application is a continuation of and claims the benefit ofpriority to U.S. patent application Ser. No. 16/804,979, filed on Feb.28, 2020, which is a continuation of and claims the benefit of priorityto U.S. application Ser. No. 15/662,580, filed Jul. 28, 2017, now U.S.Pat. No. 10,614,021, issued Apr. 7, 2020, the entirety of which isincorporated herein by reference.

TECHNICAL FIELD

Various embodiments of the present disclosure relate generally toelectronic payment infrastructure and, more particularly, to providing ascalable cloud-based device gateway.

BACKGROUND

Traditionally, merchants and other store owners have point of sale (POS)terminals and POS systems that can accept check or payment card paymentsfrom consumers for goods and services. Such POS systems may include PINpads at which a consumer may enter payment and/or personal informationin order to complete payment processing requests for purchases. Each PINpad may connect to the merchant's payment processing through a gateway.If the PIN pad is stateless then a separate gateway with a directconnection to each PIN pad may be required, thus limiting the throughputand scalability of the merchant's payment processing system. This maycause inconvenience and dissatisfaction for the merchant and themerchant's customers, possibly resulting in decreased revenue for themerchant.

The present disclosure is directed to overcoming one or more of theseabove-referenced challenges.

SUMMARY OF THE DISCLOSURE

According to certain aspects of the disclosure, systems and methods aredisclosed for processing payment transactions.

In one embodiment, a computer-implemented method is disclosed forprocessing payment transactions. The method includes: receiving aconnection request from a client device, determining whether a gatewayis available for the client device, creating a connection between theclient device and a gateway, the gateway being a previously existinggateway or a newly generated gateway, creating a message filter for theclient device on a message bus, listening for messages on the messagebus and transmitting the message to the client device by way of thegateway upon finding a message on the message bus matching the messagefilter.

According to certain aspects of the disclosure, non-transitory computerreadable media are disclosed storing a program causing a computer toexecute a method of processing payment transactions, One methodcomprises: receiving a connection request from a client device,determining whether a gateway is available for the client device,creating a connection between the client device and a gateway, thegateway being a previously existing gateway or a newly generatedgateway, creating a message filter for the client device on a messagebus, listening for messages on the message bus and transmitting themessage to the client device by way of the gateway upon finding amessage on the message bus matching the message filter.

In accordance with another embodiment, a system is disclosed forprocessing payment transactions. The system comprises: a memory havingprocessor-readable instructions stored therein; and a processorconfigured to access the memory and execute the processor-readableinstructions, which when executed by the processor configures theprocessor to perform a plurality of functions, including functions to:receive a connection request from a client device, determine whether agateway is available for the client device, create a connection betweenthe client device and a gateway, the gateway being a previously existinggateway or a newly generated gateway, create a message filter for theclient device on a message bus, listen for messages on the message bus;and upon finding a message on the message bus matching the messagefilter, transmit the message to the client device by way of the gateway.

Additional objects and advantages of the disclosed embodiments will beset forth in part in the description that follows, and in part will beapparent from the description, or may be learned by practice of thedisclosed embodiments. The objects and advantages of the disclosedembodiments will be realized and attained by means of the elements andcombinations particularly pointed out in the appended claims. As will beapparent from the embodiments below, an advantage to the disclosedsystems and methods is that a variable number of stateless PIN padclient devices may maintain connections to a merchant's paymentprocessing system. The disclosed systems and methods discussed below mayallow greater throughput and scalability of the payment processingsystem.

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory onlyand are not restrictive of the disclosed embodiments, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate various exemplary embodiments andtogether with the description, serve to explain the principles of thedisclosed embodiments.

FIG. 1 depicts an exemplary system infrastructure for electronic paymenttransactions, according to one or more embodiments.

FIG. 2 depicts an exemplary system infrastructure for a cloud baseddevice gateway, according to one or more embodiments.

FIG. 3 depicts a flowchart of a method of cloud based device gatewayconnection, according to one or more embodiments.

FIGS. 4A and 4B depict a communication flow diagram of a method of cloudbased device gateway connection, according to one or more embodiments.

FIG. 5 depicts a flowchart of a method of cloud based device gatewayconnection, according to one or more embodiments.

FIG. 6 depicts a block diagram of an electronic payment processingsystem.

FIG. 7 is a block diagram of an example computing environment, accordingto one or more embodiments.

DETAILED DESCRIPTION OF EMBODIMENTS

Various embodiments of the present disclosure relate generally toproviding a scalable cloud-based device gateway for processing paymenttransactions.

The terminology used below may be interpreted in its broadest reasonablemanner, even though it is being used in conjunction with a detaileddescription of certain specific examples of the present disclosure.Indeed, certain terms may even be emphasized below; however, anyterminology intended to be interpreted in any restricted manner will beovertly and specifically defined as such in this Detailed Descriptionsection.

A merchant payment processing system may typically include one or morepoint of sale (POS) terminals in communication with one or more personalidentification number (PIN) pads. Once a customer's transaction enteredat the POS device is ready for completion, the POS device may sendcommands to a PIN pad for interaction with the customer to complete thetransaction. This interaction may include presentation of paymentcredentials, such as a payment vehicle, and entry of customeridentification, such as a PIN, biometric information, etc. Each POSdevice will maintain communication with the associated PIN pad in orderto ensure that a customer can complete the transaction. Desirably, inorder to allow a flexible association between a PIN pad and POS device,each PIN pad may connect to the merchant's payment processing systemthrough a gateway. For example, the merchant's payment processing systemmay be accessible in a cloud environment rather than by a directconnection from the PIN pad. Thus, a PIN pad may not be directly linkedwith a particular POS device. However, it may be inefficient to providea dedicated gateway for each PIN pad. Accordingly, as discussed indetail below, the merchant payment processing system may generate a newgateway on demand based on the needs of the merchant's POS devices andPIN pads.

As shown in FIG. 6 , in an electronic payment processing system, aconsumer 602, during the checkout process with a merchant 610, pays forgoods or services from merchant 610 at a PIN Pad 128 associated with POSterminal 102. Consumer 602 may use a payment card as payment and thetransaction is processed through a payment environment 600. Becausemerchant 610 generally can use a different bank or financial institution640 than consumer 602, an acquirer processor 630 handles the financialtransactions that transfer payment between the financial institution 640of consumer 602 and that of merchant 610. Consumer 602 submits paymentinformation at the PIN Pad 128 associated with POS terminal 102 ofmerchant 610, such as by swiping his or her payment card, inserting hisor her chip-based payment card, through wireless near fieldcommunication (NFC), etc., or by any other suitable means. PIN Pad 128sends a payment request by way of a computer network 625 to an acquirerprocessor 630. Alternatively, such a request may be sent by a componentthat controls a flow of a transaction, such as point of sale (POS)engine 250 depicted in FIG. 2 . Acquirer processor 630 requests, by wayof payment network 620, an electronic transfer of funds from thereceived funds to the financial institution 640 associated with merchant610.

Merchant 610 may provide an infrastructure for processing electronicpayment requests. FIGS. 1 and 2 depict an exemplary systeminfrastructure for payment processing within a merchant environment,according to one or more embodiments.

As shown in FIG. 1 , an infrastructure 100 for processing electronicpayment requests may include one or more point of sale (POS) devices102, which may be in communication with a POS engine 106, and one ormore personal identification number (PIN) pad terminals 128, which maybe in communication with a socket gateway 124. POS devices 102 maycommunicate a sale request message over computer network 104 to POSengine 106. POS engine 106 may be embodied, for example, as middlewarethat may transmit commands to control a PIN pad 128, such as by sendinga payment request to PIN pad transaction generator 110 over computernetwork 118. PIN pad transaction generator 110 may generate one or morePIN pad commands 114 for processing by a transaction actor 112.Transaction actor 112 may take in a transaction request from the POSengine 106 and PIN pad specific commands 114 for the transaction.Transaction actor 112 may further take in expected responses from PINpad 128. Transaction actor 112 may manage the entire transaction using,for example, a state machine for the specific transaction.

Infrastructure 100 for processing electronic payment requests mayfurther include a PIN pad device gateway 120, which may providecommination with PIN pad terminals 128. PIN pad device gateway 120 mayinclude a message broker that may process incoming sales transactionmessages, a transaction service bus topic 122, and one or more devicegateways 124. PIN pad device gateway 120 will be described in greaterdetail below with respect to FIG. 2 .

As shown in FIG. 1 , infrastructure 100 may further include aconfiguration management service 130, which may provide configurationservices for PIN pad terminals 128. Configuration management service 130may include a configuration service 140, a PIN pad registry 138 and aPIN pad database 142. Configuration service 140 may, if necessary,configure the PIN pad upon connection of the PIN pad to theinfrastructure. PIN pad registry 138 and PIN pad database 142 maymaintain data associating each PIN pad with an account or merchant.Configuration management service 130 may further include a lanemanagement service 132 and a PIN Pad activator 134.

Infrastructure 100 may be embodied as a semi-integrated solution and mayfurther control the PIN pad on behalf of the POS device software. Suchcontrol may include controlling a transaction flow or sequenceincluding, for example, prompting for payment card swipe or insert,sending a transaction request for authorization, prompting for aconsumer signature, etc.

Turning to FIG. 2 , PIN pad device gateway 120 may include a message bus215, which may receive messages from a backend application or service205. The messages may be processed or published to the message bus byone or more protocol buffers 210. For example, protocol buffer 210 maytranslate the message from a communication protocol of backendapplication or service 205 to a communication protocol of message bus215. Message bus 215 may store one or more message 225. Each message maycomprise, in addition to the content of the message, additional items ofmetadata including, for example, a sender identity, a sender address, asent date and time, a sent location, a recipient identity, a recipientaddress, a topic, access permissions for individual recipients or agroup of recipients, etc.

Messages from backend application or service 205 may be intended, forexample, for one of any number of client devices 220. For example,client device 220 may be a PIN pad, such as PIN pad 128 depicted in FIG.1 . Each client device 220 may access the merchant transactionprocessing system, including message bus 215, by way of a gateway 124.For example, client device 220 may be stateless and may connect to themerchant transaction processing system through gateway 124 by way ofsocket connections, which may be based on the client ID of client device220. Connection details, such as the client ID of client device 220 maybe stored in a cache, for example, maintained by gateway 124. Gateway124 may then create a message filter on the message bus 215 if one doesnot exist, or it may update an existing message filter. The messagefilter may include identifying information of the recipient of themessage, such as client device 220. For example, the message filter mayinclude the client ID of client device 220, a message topic, a recipientaddress, etc. Such a message filter may be treated as a message topicsubscription for retrieving messages. Alternatively, gateway 124 maylisten for new messages and may read a new message if a recipient ID forthe message matches a client ID stored in its cache. If a message isread by gateway 124 based on a match of the message filter or arecipient client ID, gateway 124 may transmit the message to theassociated client device 220. Prior to transmitting the message to theassociated client device 220, gateway 124 may, if desired, translate themessage from a message bus communication protocol to a client deviceprotocol. Alternatively, such a translation may be performed by anexternal process, such as by message bus pump 108.

If a response to the message is expected, the client that sent theoriginal message may likewise register a topic subscription and listenfor matching messages. For example, protocol buffer 210 may create amessage filter on the message bus 215 if one does not exist, or it mayupdate an existing message filter to include a client ID of backendapplication or service 205. Protocol buffer 210 may subsequently listenfor new messages and may read a new message matching the message filterto be transmitted to backend application or service 205.

Message bus 215 may be controlled by or may have additional servicesperformed by a message bus pump 108. For example, message bus pump 108may translate messages from client or device communication protocols tothe communication protocol of message bus 215. Message bus pump 108 mayfurther register subscriptions for a client device or service such thatmessages meeting registered criteria are automatically retrieved frommessage bus 215. For example, a client device 220 may register a messagetopic subscription with message bus pump 108 such that when a messagewith the registered topic is stored on message bus 215, it isautomatically retrieved and transmitted to the client device 220.

The merchant transaction processing system may include any number ofclient devices 220. However, it may be inefficient or inconvenient tomaintain a dedicated gateway 124 for each possible client device 220.Accordingly, PIN pad device gateway 120 may generate a new gateway 124only when the new gateway 124 is needed. For example, a new gateway 124may be generated when a new client device 220 is connected to themerchant transaction processing system, or when an existing clientdevice 220 becomes active, or when a message intended for an existingclient device 220 is detected on message bus 215. PIN pad device gateway120 may maintain a gateway 124 for each active client device 220 and mayterminate gateway 124 when the associated client device 220 becomesinactive, thus maintaining the same number of gateways 124 and activeclient devices 220. Alternatively, PIN pad device gateway 120 maymaintain a minimum number of gateways 124 that may be greater than thenumber of active client devices 220. This may allow a transaction to beprocessed using an existing gateway 124 without the delay of generatinga new gateway 124. The newly generated gateway 124 may remain activeeven after the associated client device 220 becomes inactive, thusincreasing the pool of available gateways 124. If the number of gateways124 that are not associated with an active client device 220 exceeds athreshold then one or more gateways 124 may be terminated in order tofree allocated resources.

Each gateway 124 may provide services for a single client device 220, asdescribed above, or each gateway 124 may provide services for multipleclient devices 220. In this case, a newly connected or activated clientdevice 220 may be associated with a gateway 124 having capacity toservice an additional client device 220. If no gateway 124 has capacityto service an additional client device 220, then an additional gateway124 may be generated when a new client device 220 is connected to themerchant transaction processing system, or when an existing clientdevice 220 becomes active, or when a message intended for an existingclient device 220 is detected on message bus 215. When a client device220 becomes inactive, the associated gateway 124 may be open toproviding services for an additional client device 220. If a gateway 124is not servicing any client devices 220 then the gateway 124 may beterminated in order to free allocated resources, or the gateway 124 maybe maintained in order to allow a transaction to be processed using theexisting gateway 124 without the delay of generating a new gateway 124.If the total capacity of active gateways 124 to provide services toadditional client devices 220 exceeds a threshold then one or moregateways 124 may be terminated in order to free allocated resources.

According to one or more embodiments, the components of infrastructure100 may be connected by one or more computer networks, such as, forexample a local area network (LAN) or a wireless network, such as, forexample, a Wi-Fi network. However, other network connections among thecomponents of infrastructure 100 may be used, such as, for example, awide area network (WAN), the internet, or the cloud. According to one ormore embodiments, the components of infrastructure 100 may operate toprovide cloud based device gateway connection. Methods of cloud baseddevice gateway connection will be discussed with respect to FIGS. 3-5below. Functions of the components of infrastructure 100 will bedescribed below with respect to exemplary methods for cloud based devicegateway connection.

FIG. 3 depicts a flowchart of a method of cloud based device gatewayconnection, according to one or more embodiments. Turning to FIG. 3 , inoperation 305, the cloud device gateway may receive a connection requestfrom a client device, such as PIN pad 128 depicted in FIG. 1 . Inoperation 310, the cloud device gateway may determine whether a socketgateway, such as PIN pad socket gateway 124 depicted in FIGS. 1 and 2 ,is available for the client device. If no socket gateway is availablefor the client device, then in operation 315, the cloud device gatewaymay create new socket gateway to be accessed by the client device.Alternatively, if no socket gateway is available for the client device,then in operation 320, the cloud device gateway may select an availablesocket gateway to be accessed by the client device. Once a socketgateway is available to be accessed by the client device, in operation325, the cloud device gateway may create a connection between the clientdevice and the socket gateway. In order to route messages to the clientdevice, in operation 330, the cloud device gateway may create new topicfor the client device, such as a topic subscription or on a message bus,such as transaction service bus 122 depicted in FIG. 1 . Thereafter, inoperation 335, the cloud device gateway may listen for messages onmessage bus, and upon finding a message addressed to the client device,in operation 340, the cloud device gateway may transmit the message tothe client device by way of the socket gateway. In operation 345, thecloud device gateway may receive a response from the client device byway of the gateway, and in operation 350, the cloud device gateway mayinsert the response onto message bus to be routed to a destinationdevice or process, as appropriate.

FIGS. 4A and 4B depict a communication flow diagram of a method of cloudbased device gateway connection, according to one or more embodiments.As shown in FIGS. 4A and 4B, in operation 402, a client, such as PIN pad128 depicted in FIG. 1 , may request a gateway connection from a devicegateway, such as cloud based device gateway 120 depicted in FIG. 1 . Inoperation 404, the cloud device gateway may determine whether a socketgateway, such as PIN pad socket gateway 124 depicted in FIG. 1 , isavailable for the client device. In operation 406, the cloud devicegateway may create a new socket gateway if none is available. Inoperation 408, the cloud device gateway may create a connection betweenthe client device and the socket gateway. In operation 410, the clouddevice gateway may create new topic for the client device on a messagebus, such as transaction service bus 122 depicted in FIG. 1 .Thereafter, in operation 412, the cloud device gateway may listen formessages on the message bus. In operation 414, a backend application orservice, such as PIN pad transaction generator 110 depicted in FIG. 1 ,may receive a sales transaction, such as from POS engine 106 depicted inFIG. 1 . In operation 416, the backend application or service maytransmit the sales transaction to a protocol buffer, such as protocolbuffer 210 depicted in FIG. 2 . In operation 418, the protocol buffermay translate the sale transaction to a message bus protocol. Inoperation 420, the protocol buffer may insert a message on the messagebus for the sales transaction. In operation 422, the cloud devicegateway may detect a message on the message bus intended for the client.In operation 424, the cloud device gateway may retrieve the message fromthe message bus. In operation 426, the cloud device gateway maytranslate the message to a client protocol. In operation 428, the clouddevice gateway may transmit the message to the client. In operation 430,the client may process the sales transaction. In operation 432, theclient may transmit a response to the cloud device gateway. In operation434, the cloud device gateway may translate the response to the messagebus protocol. In operation 436, the cloud device gateway insert theresponse on the message bus. In operation 438, the protocol buffer mayretrieve the response from the message bus. In operation 440, theprotocol buffer may translate the response to the backend protocol. Inoperation 442, the protocol buffer may transmit the response to thebackend application or service.

FIG. 5 depicts a flowchart of a method of cloud based device gatewayconnection, according to one or more embodiments, which may beperformed, for example, by a device gateway, such as cloud based devicegateway 120 depicted in FIG. 1 . As shown in FIG. 5 , in operation 510,the device gateway may receive a sales transaction from a backendapplication or service, such as PIN pad transaction generator 110depicted in FIG. 1 . In operation 520, the device gateway may translatethe sales transaction message to a message bus protocol. In operation530, the device gateway may insert the translated sales transactionmessage onto a message bus, such as transaction service bus 122 depictedin FIG. 1 . In operation 540, the device gateway may receive a clientdevice response from message bus. In operation 550, the device gatewaymay translate the client device response to a backend application orservice protocol. In operation 560, the device gateway may transmit theresponse to the backend application or service.

Any suitable system infrastructure may be put into place to provide acloud based device gateway. FIGS. 1, 2, 6 , and the following discussionprovide a brief, general description of a suitable computing environmentin which the present disclosure may be implemented. In one embodiment,any of the disclosed systems, methods, and/or graphical user interfacesmay be executed by or implemented by a computing system consistent withor similar to that depicted in FIGS. 1, 2 and 6 . Although not required,aspects of the present disclosure are described in the context ofcomputer-executable instructions, such as routines executed by a dataprocessing device, e.g., a server computer, wireless device, and/orpersonal computer. Those skilled in the relevant art will appreciatethat aspects of the present disclosure can be practiced with othercommunications, data processing, or computer system configurations,including: Internet appliances, hand-held devices (including personaldigital assistants (“PDAs”)), wearable computers, all manner of cellularor mobile phones (including Voice over IP (“VoIP”) phones), dumbterminals, media players, gaming devices, virtual reality devices,multi-processor systems, microprocessor-based or programmable consumerelectronics, set-top boxes, network PCs, mini-computers, mainframecomputers, and the like. Indeed, the terms “computer,” “server,” and thelike, are generally used interchangeably herein, and refer to any of theabove devices and systems, as well as any data processor.

Aspects of the present disclosure may be embodied in a special purposecomputer and/or data processor that is specifically programmed,configured, and/or constructed to perform one or more of thecomputer-executable instructions explained in detail herein. Whileaspects of the present disclosure, such as certain functions, aredescribed as being performed exclusively on a single device, the presentdisclosure may also be practiced in distributed environments wherefunctions or modules are shared among disparate processing devices,which are linked through a communications network, such as a Local AreaNetwork (“LAN”), Wide Area Network (“WAN”), and/or the Internet.Similarly, techniques presented herein as involving multiple devices maybe implemented in a single device. In a distributed computingenvironment, program modules may be located in both local and/or remotememory storage devices.

Aspects of the present disclosure may be stored and/or distributed onnon-transitory computer-readable media, including magnetically oroptically readable computer discs, hard-wired or preprogrammed chips(e.g., EEPROM semiconductor chips), nanotechnology memory, biologicalmemory, or other data storage media. Alternatively, computer implementedinstructions, data structures, screen displays, and other data underaspects of the present disclosure may be distributed over the Internetand/or over other networks (including wireless networks), on apropagated signal on a propagation medium (e.g., an electromagneticwave(s), a sound wave, etc.) over a period of time, and/or they may beprovided on any analog or digital network (packet switched, circuitswitched, or other scheme).

The systems and processes described above may be performed on or betweenone or more computing devices. FIG. 7 illustrates an example computingdevice. A computing device 700 may be a server, a computing device thatis integrated with other systems or subsystems, a mobile computingdevice such as a smart phone, a cloud-based computing ability, and soforth. The computing device 700 may be any suitable computing device aswould be understood in the art, including without limitation, a customchip, and embedded processing device, a tablet computing device, a POSterminal associated with the merchant 110, a back-office system of amerchant 110, a personal data assistant (PDA), a desktop, laptop,microcomputer, and minicomputer, a server, a mainframe, or any othersuitable programmable device. In various embodiments disclosed herein, asingle component may be replaced by multiple components and multiplecomponents may be replaced by single component to perform a givenfunction or functions. Except where such substitution would not beoperative, such substitution is within the intended scope of theembodiments.

The computing device 700 includes a processor 702 that may be anysuitable type of processing unit, for example a general-purpose centralprocessing unit (CPU), a reduced instruction set computer (RISC), aprocessor that has a pipeline or multiple processing capabilityincluding having multiple cores, a complex instruction set computer(CISC), a digital signal processor (DSP), application specificintegrated circuits (ASIC), a programmable logic devices (PLD), and afield programmable gate array (FPGA), among others. The computingresources may also include distributed computing devices, cloudcomputing resources, and virtual computing resources in general.

The computing device 700 also includes one or more memories 706, forexample read-only memory (ROM), random access memory (RAM), cache memoryassociated with the processor 702, or other memory such as dynamic RAM(DRAM), static RAM (SRAM), programmable ROM (PROM), electricallyerasable PROM (EEPROM), flash memory, a removable memory card or disc, asolid-state drive, and so forth. The computing device 700 also includesstorage media such as a storage device that may be configured to havemultiple modules, such as magnetic disk drives, floppy drives, tapedrives, hard drives, optical drives and media, magneto-optical drivesand media, compact disk drives, Compact Disc Read Only Memory (CD-ROM),compact disc recordable (CD-R), Compact Disk Rewritable (CD-RW), asuitable type of Digital Versatile Disc (DVD) or Blu-ray disc, and soforth. Storage media such as flash drives, solid-state hard drives,redundant array of individual discs (RAID), virtual drives, networkeddrives and other memory means including storage media on the processor702, or memories 706 are also contemplated as storage devices. It may beappreciated that such memory may be internal or external with respect tooperation of the disclosed embodiments. It may be appreciated thatcertain portions of the processes described herein may be performedusing instructions stored on a computer readable medium or media thatdirect computer system to perform the process steps. Non-transitorycomputable-readable media, as used herein, comprises allcomputer-readable media except for transitory, propagating signals.

Networking communication interfaces 708 may be configured to transmitto, or receive data from, other computing devices 700 across a network712. The network and communication interfaces 708 may be an Ethernetinterface, a radio interface, a Universal Serial Bus (USB) interface, orany other suitable communications interface and may include receivers,transmitter, and transceivers. For purposes of clarity, a transceivermay be referred to as a receiver or a transmitter when referring to onlythe input or only the output functionality of the transceiver. Examplecommunication interfaces 708 may include wire data transmission linkssuch as Ethernet and TCP/IP. The communication interfaces 708 mayinclude wireless protocols for interfacing with private or publicnetworks 712. For example, the network and communication interfaces 708and protocols may include interfaces for communicating with privatewireless networks such as Wi-Fi network, one of the IEEE 802.11x familyof networks, or another suitable wireless network. The network andcommunication interfaces 708 may include interfaces and protocols forcommunicating with public wireless networks 708, using for examplewireless protocols used by cellular network providers, including CodeDivision Multiple Access (CDMA) and Global System for MobileCommunications (GSM). A computing device 700 may use network andcommunication interfaces 708 to communicate with hardware modules suchas a database or data store, or one or more servers or other networkedcomputing resources. Data may be encrypted or protected fromunauthorized access.

In various configurations, the computing device 700 may include a systembus 710 for interconnecting the various components of the computingdevice 700, or the computing device 700 may be integrated into one ormore chips such as programmable logic device or application specificintegrated circuit (ASIC). The system bus 710 may include a memorycontroller, a local bus, or a peripheral bus for supporting input andoutput devices 704, and communication interfaces 708. Example input andoutput devices 704 include keyboards, keypads, gesture or graphicalinput devices, motion input devices, touchscreen interfaces, one or moredisplays, audio units, voice recognition units, vibratory devices,computer mice, and any other suitable user interface.

The processor 702 and memory 706 may include nonvolatile memory forstoring computable-readable instructions, data, data structures, programmodules, code, microcode, and other software components for storing thecomputer-readable instructions in non-transitory computable-readablemediums in connection with the other hardware components for carryingout the methodologies described herein. Software components may includesource code, compiled code, interpreted code, executable code, staticcode, dynamic code, encrypted code, or any other suitable type of codeor computer instructions implemented using any suitable high-level,low-level, object-oriented, visual, compiled, or interpreted programminglanguage.

Other embodiments of the disclosure will be apparent to those skilled inthe art from consideration of the specification and practice of theinvention disclosed herein. It is intended that the specification andexamples be considered as exemplary only, with a true scope and spiritof the invention being indicated by the following claims.

What is claimed is:
 1. A method of processing payment transactions,comprising: receiving a message intended for a stateless personalidentification number (PIN) pad among a plurality of stateless PIN pads;generating a gateway storing state information for the stateless PINpad, including an address of the stateless PIN pad, based on receivingthe message intended for the stateless PIN pad; and transmitting themessage to the stateless PIN pad by way of the generated gateway,wherein the generated gateway is configured to maintain a connection toonly the stateless PIN pad among the plurality of stateless PIN pads. 2.The method of claim 1, the method further comprising: receiving aconnection request from another stateless PIN pad among the plurality ofstateless PIN pads; creating a message filter for the another statelessPIN pad on a message bus; listening for messages on the message bus; andupon finding a message on the message bus matching the message filterfor the another stateless PIN pad, translating the message from amessage bus communication protocol to a communication protocol ofanother stateless PIN pad.
 3. The method of claim 2, wherein the messagefilter matches one or more of a message topic, a PIN pad identifier, arecipient identity, and a recipient address.
 4. The method of claim 1,wherein the generated gateway is terminated after the stateless PIN padassociated with the generated gateway disconnects from the generatedgateway or is terminated.
 5. The method of claim 1, wherein thegenerated gateway is among a plurality of gateways, and wherein thegenerated gateway is terminated when a number of gateways among theplurality of gateways that are not connected to a stateless PIN padamong the plurality of stateless PIN pads exceeds a threshold.
 6. Acomputer system for processing payment transactions, the systemcomprising: a memory having processor-readable instructions storedtherein; and a processor configured to access the memory and execute theprocessor-readable instructions, which when executed by the processorconfigures the processor to perform a plurality of functions, includingfunctions to: receive a message intended for a stateless personalidentification number (PIN) pad among a plurality of stateless PIN pads;generate a gateway storing state information for the stateless PIN pad,including an address of the stateless PIN pad, based on receiving themessage intended for the stateless PIN pad; and transmit the message tothe stateless PIN pad by way of the generated gateway, wherein thegenerated gateway is configured to maintain a connection to only thestateless PIN pad among the plurality of stateless PIN pads.
 7. Thecomputer system of claim 6, wherein the plurality of functions performedby the processor when executing the processor-readable instructionsfurther includes functions to: receive a connection request from anotherstateless PIN pad among the plurality of stateless PIN pads; create amessage filter for the another stateless PIN pad on a message bus;listen for messages on the message bus; and upon finding a message onthe message bus matching the message filter for the another statelessPIN pad, translate the message from a message bus communication protocolto a communication protocol of the another stateless PIN pad.
 8. Thecomputer system of claim 7, wherein the message filter matches one ormore of a message topic, a PIN pad identifier, a recipient identity, anda recipient address.
 9. The computer system of claim 6, wherein thegenerated gateway is among a plurality of gateways, and wherein thegenerated gateway is terminated when a number of gateways among theplurality of gateways that are not connected to a stateless PIN padamong the plurality of stateless PIN pads exceeds a threshold.
 10. Anon-transitory computer readable medium storing a program causing acomputer to execute a method of processing payment transactions, themethod comprising: receiving a message intended for a stateless personalidentification number (PIN) pad among a plurality of stateless PIN pads;generating a gateway storing state information for the stateless PINpad, including an address of stateless PIN pad, based on receiving themessage intended for the stateless PIN pad; and transmitting the messageto the stateless PIN pad by way of the generated gateway, wherein thegenerated gateway is configured to maintain a connection to only thestateless PIN pad.
 11. The non-transitory computer readable mediumaccording to claim 10, the method further comprising: receiving aconnection request from another stateless PIN pad among the plurality ofstateless PIN pads; creating a message filter for the another statelessPIN pad on a message bus; listening for messages on the message bus; andupon finding a message on the message bus matching the message filterfor the another stateless PIN pad, translating the message from amessage bus communication protocol to a communication protocol of theanother stateless PIN pad.
 12. The non-transitory computer readablemedium according to claim 11, wherein the message filter matches one ormore of a message topic, a PIN pad identifier, a recipient identity, anda recipient address.
 13. The non-transitory computer readable mediumaccording to claim 10, wherein the generated gateway is terminated afterthe stateless PIN pad associated with the generated gateway disconnectsfrom the generated gateway or is terminated.
 14. The non-transitorycomputer readable medium according to claim 10, wherein the generatedgateway is among a plurality of gateways, and wherein the generatedgateway is terminated when a number of gateways among the plurality ofgateways that are not connected to a stateless PIN pad among theplurality of stateless PIN pads exceeds a threshold.